Bump version to 0.1.2: 0.1.1 published but the workflow bump push was rejected - #55
Conversation
…kflow's own bump push was rejected by branch protection
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. WalkthroughThe ChangesRelease metadata
Estimated code review effort: 1 (Trivial) | ~2 minutes Merge Risk: ⚪ Minimal · up to This localized metadata change updates the package version to 0.1.2 and restores the release-version sequence; no actionable merge-blocking risk remains after normal checks and review. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Restores the release-lifecycle invariant after today's merge train: run 32256792684 successfully published
rain-datacontract0.1.1 to Soldeer (registry timestamp 2026-08-19T13:13:19Z, verified via api.soldeer.xyz), then had its own post-publish bump commit rejected by branch protection (GH006: Protected branch update failed for refs/heads/main). Main therefore still says 0.1.1 while 0.1.1 is published — the next content-changing push would fail the autopublish gate (local == published), which is exactly the #24 disease again.This commit is the byte-equivalent of what the workflow tried to push:
[external.package].version0.1.1 → 0.1.2 (next unpublished patch).Sibling context: rain.solmem's main is unprotected, so its identical workflow pushes its bump fine. The push-back-vs-protection policy question is tracked separately; this PR only restores the invariant.
QA
🤖 Generated with Claude Code
Summary by CodeRabbit